Choosing a Service Template
When you install SequeLink Server, at least one SequeLink data access service, and one or more service templates determined by the SequeLink Server, are installed. You can use the SequeLink Manager to create additional services based on the SequeLink service templates and to modify the default service attributes defined in the service templates:
In most cases, the SequeLink service templates provide a configuration that can be used without any modification. However, some service templates provide additional transliteration capabilities. You must select the service template that meets the transliteration requirements of your application.
NOTES:
Table 12-1 lists the transliteration environments that the service templates support on Linux/UNIX/Windows.
Table 12-1. Selecting a Service Template on Linux/UNIX/Windows Service Template Transliteration Environment Standard service templateAutomatically sets ServiceCodePage=Default (see "ServiceCodePage")
- ODBC and ADO Clients: The database code page is a 7-bit or 8-bit code page and matches the code page of the client application.
- JDBC and .NET Clients: The database code page is a 7-bit or 8-bit code page and has a binary-compatible transliteration to UTF-16.
- Operating system (OS) and database code pages use a single-byte or multi-byte character set.*
Service template with enhanced code page supportAutomatically sets ServiceCodePage="Database" (see "ServiceCodePage") The database contains Unicode data or the operating system and database code pages differ.*If you want enhanced code page support for the SequeLink Server for ODBC Socket or SequeLink Server for Sybase, we recommend using the UTF-16 encoding version of the template. * Not available for SequeLink Server for Informix, SequeLink Server for DB2 UDB on z/OS USS, or SequeLink Server for JDBC Socket.